Correct repository fields in package.json files #13416
Merged
+8
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a super minor thing, but the
package.jsonfiles currently have inconsistent/invalid repository metadata.I noticed because I configured Renovate to group this repo's updates on a
tailwindcss-monorepobranch, but@tailwindcss/viteupdates remained ungrouped. I am pretty sure it's the slightly invalid metadata that's the problem.This PR would update
"repository"to exactly match the examples in the NPM docs.This change may also fix the missing repository links on the NPM pages for your new packages, though I'm a lot less sure of that!